http server
Device Configuration
The configuration of server related parameters can be set through the webpage on the device side, as shown in the following figure:
Field | explain |
---|---|
Agreement | Protocol, currently supports HTTP,HTTPS |
Server address | The IP address or domain name of the server. In the example, the HTTP server address is the IP address of the computer where the test server is located. In actual production environments, please confirm with the server side |
URL path | The URL for event reporting. In the example, the test server's URL is /api/v1/event/pull. Please confirm with the server side in the actual production environment |
Port | Server port, in the example, the port of the HTTP test server is 8081. Please confirm with the server in the actual production environment |
Authentication mode | If "none" is selected, authentication will be enabled. Choosing "key" and "device token" is mandatory. If not selected, it can be left blank |
Secret key | Device Secret key, the serial number of the camera in the example, please confirm with the server in the actual production environment |
Device token | Device token, usually the device SN |
Timeout period | Device heartbeat timeout time |
Registration status | Device registration status |
- Attention: Click the "Test" button, and the device will use the configured parameter items to report heartbeat events to verify whether the parameters are correct. If successful, it will prompt "Test successful"
Test equipment reporting function
Click the 'Test' button in the event center of the device's webpage, and the device will send a heartbeat request to the testing server
After receiving the heartbeat request from the device, the test server will print the heartbeat request information (as shown in the figure below) and respond with a heartbeat response to the device. Please refer to the specific content of the response message for details heartbeat
- Attention: If the server does not respond or the response content is empty, the device will not report the event to the server
Trigger event
After triggering an event on the device side, the device will report the event to the server, and the server will print the reported information upon receiving it, as shown in the following figure